Method and system for digital document management on a mobile device

ABSTRACT

A method and system are described for tracking a process of provisioning, by a middleware server to a portable device in a mobile payment system, electronic wallet data for authorizing a payment transaction. In an embodiment, a user request for a payment account product is transmitted by the portable device to the middleware server. In response, the middleware server initiates a provisioning process for the requested payment account product, including storing status data indicative of an initiated state of the provisioning process. The middleware server then transmits a digital document to the portable device, including information that must be viewed by the user, and updates the status data indicative of a transmitted state of the digital document. In response to receiving an indication that the digital document has been viewed, the middleware server updates the stored status data indicative of a digital document viewed state. The middleware then provisions an electronic wallet data for the requested payment account product to the portable device.

FIELD OF THE INVENTION

This invention relates to a mobile payment account system. Moreparticularly, the invention relates to an improved process ofprovisioning of a mobile payment account on a mobile device andmanagement of associated digital documents.

BACKGROUND OF THE INVENTION

Mobile payment account systems are generally known, in which portableelectronic devices are configured to provide payment from an electronicwallet. Typically, these portable electronic devices are configured toenable a contactless communication with a merchant Point Of Sale (POS)terminal to carry out a payment transaction, for example, using nearfield communication (NFC) technology. As described in the commonly ownedco-pending U.S. patent application Ser. No. 12/891,866, entitled “METHODAND SYSTEM FOR ELECTRONIC WALLET ACCESS”, filed Oct. 15, 2010, and U.S.patent application Ser. No. 12/905,419, entitled “MOBILE PAYMENTSYSTEM”, filed Sep. 28, 2010, both of which are incorporated herein byreference in their entirety, activated mobile payment account data canbe stored in the secure memory of the portable electronic device whichcan then be used to carry out transactions with the merchant electronicPOS terminal via a NFC link. Systems described in the above-referencedcommonly owned applications advantageously provide the customer with theability to apply for a payment product that, once approved, isimmediately provisioned and activated on the mobile device, thusallowing the customer to immediately make purchases using the activatedmobile payment account. As described in US'866, provisioning of a mobilepayment account, for example in response to an instant provisioningrequest from the mobile device, involves creation and communication ofdata for the mobile payment account to the mobile device. Activation ofthe mobile payment account provisioned on the mobile device typicallyinvolves authentication of the user before the mobile payment account isenabled for use in the mobile payment system.

Generally, issuing banks have issued paper terms and conditions (T&C)and cardmember agreements (CMA) to support traditional credit cardprograms. In the case of an instant credit offer, (e.g. retail) thecustomer is presented the CMA in paper form as part of the paperapplication. In a non-instant credit offer (e.g. mail channels), the CMAis delivered to the customer in paper format, via US Mail as part oftheir new cardmember fulfillment kit. In a web apply channel, thedisclosure is generally provided digitally, allowing the customer tosimply print out the disclosure, and a follow up hard copy is deliveredby post in the fulfillment kit. The systems described in theabove-referenced co-pending 866 and '419 applications present an unusualproblem in that “instant credit” for a mobile user assumes not onlytraditional instant credit (such as the retail scenario above), but thatit provides the customer with the ability to immediately provision andactivate the mobile payment account on the mobile device, thus providingthe customer with the ability to immediately begin making purchases.This mobile instant credit availability requires the issuer to considera new, digital disclosure solution.

SUMMARY OF THE INVENTION

In one aspect of the present invention, a computer-implemented method isprovided for tracking a process of provisioning, by a middleware serverto a portable device in a mobile payment system, electronic wallet datafor authorizing a payment transaction. The method comprisestransmitting, by the portable device to the middleware server, a userrequest for a payment account product; initiating, by the middlewareserver responsive to the received user request, a provisioning processfor the requested payment account product, including storing status dataindicative of an initiated state of the provisioning process;transmitting, by the middleware server to the portable device, a digitaldocument including information that must be viewed by the user andupdating the stored status data indicative of a digital documenttransmitted state (that is, the transmitted state of the digitaldocument); receiving, by the middleware server from the portable device,an indication that the digital document has been viewed by the user, andin response updating the stored status data indicative of a digitaldocument viewed state; and provisioning, by the middleware server to theportable device, electronic wallet data for the requested paymentaccount product.

Generally, the digital document is a terms and conditions (T&C) digitaldocument or a cardmember agreement (CMA). In a further aspect, the T&Cdigital document is delivered to the portable device as apre-application disclosure and the CMA is delivered to the portabledevice as a post-application disclosure.

In another aspect, the process of delivering the CMA is integratedwithin the payment product activation process which occurs on thehandset. Once the customer has been given the option to view their CMAand elects to continue the account activation process, the paymentaccount can then be fully activated and made available for immediateuse.

In another aspect of the present invention, a mobile payment accountsystem is provided, comprising a portable device in communication with amiddleware server, wherein the portable device transmits, to themiddleware server, a user request for a payment account product; andwherein the middleware server : initiates, responsive to the receiveduser request, a provisioning process for the requested payment accountproduct, including storing status data indicative of an initiated stateof the provisioning process; transmits, to the portable device, adigital document including information that must be viewed by the userand updates the stored status data indicative of a digital documenttransmitted state; receives, from the portable device, an indicationthat the digital document has been viewed by the user, and in response,updates the stored status data indicative of a digital document viewedstate; and provisions, to the portable device, electronic wallet datafor the requested payment account product.

In yet a further aspect there is provided a portable device in the abovesystem and a computer program arranged to carry out the above methodwhen executed by components of a mobile payment system.

BRIEF DESCRIPTION OF THE DRAWINGS

There now follows, by way of example only, a detailed description ofembodiments of the present invention, with references to the figuresidentified below.

FIG. 1 is a block diagram showing the main components of a mobilepayment system according to an embodiment of the invention;

FIG. 2 is a block diagram showing the main hardware and/or softwareelements of a mobile device shown in FIG. 1 according to an embodiment;

FIG. 3 is a flow diagram illustrating the main processing stepsperformed by the mobile device of FIGS. 1 and 2 in a process forapplying for a new mobile payment account product according to anembodiment;

FIG. 4, which comprises FIGS. 4 a to 4 f, illustrates a sequence ofscreens displayed by the mobile device to the user during the process ofapplying for a new mobile payment account product; and

FIG. 5 schematically illustrates a digital document structure forfacilitating enhanced monitoring and tracking of user navigation throughthe document, according to an alternate embodiment of the presentinvention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Referring to FIG. 1, a mobile payment system 1 according to anembodiment comprises a mobile device 3, a merchant's electronic Point ofSale (POS) terminal 5 as commonly known in the field, and an accountmanagement system 7 associated with a payment account issuer 10. Themobile device 3, merchant's electronic POS terminal 5, and the accountmanagement system 7 associated with the payment account issuer 10communicate electronically with one another. The account managementsystem 7 provides for mobile payment account creation and activation,transaction authorization, and other related functionalities, asdescribed in the above-referenced co-pending U.S. patent applicationSer. Nos. 12/891,866 and 12/905,419. As will be described below, theaccount management system 7 can include a communications server 13 and aTrusted Service Manager (TSM) server 18 for facilitating communicationbetween the middleware server 16 and the mobile device 3. The paymentaccount issuer 10 can include a payment processing (authorization andfraud monitoring) system 10 a for authorizing and effecting paymenttransactions from payment accounts associated with the payment accountissuer 10, in response to payment transaction instructions received viaa payment association network 17. In this embodiment, the mobile device3 and the electronic POS terminal 5 communicate with one another over acontactless communication link 9 via respective contactlesscommunication interfaces 39 a, 39 b. It is appreciated that thiscontactless communication link 9 may be a near field communication (NFC)link, an infra-red link, an ultra-sonic link, an optical link, a radiofrequency (eg. RFID) link, a wireless link such as Bluetooth or Wi-Fibased on the IEEE 802.11 standards, or any other communication link thatdoes not require direct physical contact. The mobile device 3 cancommunicate with the account management system 7 over a cellulartelephone network 11 via a cellular network interface 33.

As shown in FIG. 1, the mobile device 3 in this embodiment includes asecure memory 4 storing payment account data (that is, electronic walletdata) 6 for one or more mobile payment accounts that have been set up onthe mobile device 3. The secure memory 4 can be a Universal IntegratedCircuit Card (UICC) secure element, any other secure memoryconfiguration, such as an embedded secure element chip, or as part of aperipheral accessory device to the mobile device 3, such as a microSecure Digital card—otherwise known as a micro SD card, as are known inthe art. Other forms of mobile handset software and/or hardware can beimplemented to provide built-in secure electronic wallet functionalityfor accessing the secure memory 4, including encryption and decryptionof the payment account data 6, as necessary. The mobile device 3 isconfigured with built-in functionality providing access to secure memoryon the Subscriber Identity Module (SIM) card in the mobile device 3. Inthe present embodiment, payment account data 6 for a mobile paymentaccount that is securely stored in the mobile device 3 includes dataidentifying a user's account at a payment account issuer 10 from whichfunds can be transferred to the merchant bank to complete a transaction,via a payment association network 17. The payment account data 6 canadditionally include data defining an amount of pre-paid funds that havebeen transferred from the user's payment account issuer 10 to thatmobile payment account. In this way, the electronic wallet can include apayment account linked to multiple funding sources, such as a pre-paidaccount, deposit account and/or credit account. As an alternative, theelectronic wallet can include a plurality of mobile payment accounts,each linked to a respective funding source.

As will be described below, a user associated with the mobile device 3can search and apply for new mobile payment account products that areavailable for the user. In this embodiment, the mobile payment system 1is configured to enable the user to apply for a new mobile paymentaccount product directly from the mobile device 3, includingprovisioning and activation of the requested mobile payment account onceapproved by the account management system and/or payment account issuer,as well as providing, monitoring and receiving acceptance of digitaldisclosure documentation during the application process. In this way, auser is able to efficiently apply for a new mobile payment accountproduct solely through the mobile device 3, and the account managementsystem 7 is able to advantageously track the application process of theuser. For example, the application process of the user may be trackedfrom the initial user selection of a menu option to browse for eligibleproducts, through the user viewing and accepting specific and crucialterms, conditions and agreement clauses set out in digital disclosuredocuments particular to a product, and finally through approval andactivation of a mobile payment account product on the user's mobiledevice 3.

The mobile device 3 also includes a payment account wallet applicationmodule 8 storing processing instructions (in accordance with a preferredembodiment of the present invention processing instructions arecomputer-implementable instructions) used to control the operation ofthe mobile device 3, to facilitate the application for and management ofone or more mobile payment accounts on the mobile device 3 and to handlethe process of conducting a transaction with a merchant via theelectronic POS terminal 5. The transaction with a merchant via theelectronic POS terminal is facilitated using a mobile payment account onthe mobile device 3 to effectively transfer funds from the mobilepayment account on the mobile device 3, or an associated payment accountissuer 10, to the merchant. It is appreciated that the payment accountwallet application module 8 can be implemented as one or more softwarecomponents of an operating system running on the mobile device 3 orimplemented as one or more separate software applications installed onthe mobile device 3. Such software applications can be configured to runas background applications on the mobile device 3 that monitor receiptof messages or events and activate upon receipt of appropriate messagesor events so as to carry out the above operations. The softwareapplications can alternatively be launched by the user. Alternatively,the payment account wallet application module 8 is stored in the securememory 4, and is loaded into a virtual machine of the mobile device 3 toprovide the functionality of the present embodiment.

A secure mobile payment account provisioning and activation process canbe carried out between the mobile device 3 and the account managementsystem 7, as described in the above referenced co-pending U.S. patentapplication Ser. No. 12/891,866. The activated mobile payment accountdata stored in the secure memory 4 of the mobile device 3 can then beused to carry out transactions with a merchant electronic POS terminal 5via the contactless communication link 9, whereby a requested amount offunds can be transferred from the mobile payment account stored in themobile device 3 to the merchant's bank 12. Techniques and protocols forimplementing the authorization and transfer of funds between themerchant POS terminal 5, the merchant bank 12, and the payment accountissuer 10 via the payment association network 17 are well known to thoseskilled in the art and are therefore not described further herein.

The account management system 7 in the mobile payment system 1 will nowbe described in more detail with reference to FIG. 1, which shows theelements of the account management system 7 used in embodiments of thepresent invention. The account management system 7 includes acommunications server 13, a middleware server 16, and a TSM server 18,which communicate electronically with one another. In this embodiment,the communications server 13, middleware server 16, and TSM server 18communicate with one another via secure network links over a privateLocal Area Network (LAN), a Virtual Private Network (VPN) connection, orother dedicated secure connection. It is appreciated that, although thecomponents of the account management system 7 in this embodiment areprovided as separate servers, one or more of the servers could beprovided as software and/or hardware modules in the same server.

As shown in FIG. 1, the data is communicated between the mobile device 3and the middleware server 16 over the cellular telephone network 11 viaa cellular telephone network interface 14 of the communications server13. The TSM server 18 performs logical data preparation of the data tobe communicated to the mobile device by forming appropriate commands tobe written to the secure memory 4 of the mobile device 3. It isappreciated that the precise form of the data depends on the particularimplementation of the secure memory 4 of the mobile device 3 and/or thepayment association scheme program for facilitating payment. The TSMserver 18 can also perform encryption of the data, for example, of thesensitive payment account information, for example, payment keys, in themobile payment account data 6. The TSM server 18 then passes theencrypted data to the mobile device 3 via the communications server 13and the cellular telephone network 11.

The communications server 13 can also include a separate TSM unit 15 forsecurely routing the data to the mobile device 3. In the above example,the TSM unit 15 in the communications server 13 would not access any ofthe sensitive portions of the encrypted data that are routed to themobile device 3 via the cellular telephone network interface 14.

FIG. 2 shows the elements of a mobile device 3 according to anembodiment of the present invention. In this embodiment, the mobiledevice 3 is a mobile handset. As shown in FIG. 2, the mobile handsetoperating system and hardware includes a user interface 22 arranged toprocess inputs from a keypad 23 and to control output on a display 25.The keypad 23 and display 25 may be provided as separate hardwareentities of the mobile device 3, or alternatively, is provided as anintegrated entity such as a touch sensitive display screen userinterface. The mobile device 3 can also include components included incommonly known mobile handsets, such as a microphone, an earpiecespeaker, a camera and a controller, and/or a GPS receiver etc., whichare not shown. A working memory 27 is provided for use by the handsetoperating system and hardware units 21.

Software and data can be transferred via the cellular network interface33 or via a different data communication link interface 48 in the formof signals 49, which may be electronic, electromagnetic, optical, orother signals capable of being received by the data communication linkinterface 48 via a communication path 50 that carries the signals 49 andmay be implemented using wire or cable, fiber optics, a physical phoneline, a wireless link, a radio frequency link, or any other suitablecommunication channel, including any combination of suitablecommunication channels. It is appreciated that the communication path 50can be linked or merged with the communication path from the cellularnetwork interface 33 to the cellular telephone network 11.

As mentioned above, the mobile device 3 includes a secure memory 4. Themobile device 3 is operable to receive the payment account data 6 andactivation request messages from and send validation messages to theaccount management system 7 via the cellular telephone network interface33 and the cellular telephone network 11. The mobile device 3 is alsooperable to store the received payment account data 6 in the securememory 4. The mobile device 3 is also operable to receive transactionauthorization request messages from and send authorization messages tothe merchant's POS terminal 5 via the contactless communications linkinterface 39 and the contactless communication link 9. It is appreciatedthat communication between a POS terminal 5 and the mobile device 3 caninvolve transmission of data in a single direction from the mobiledevice 3 to the POS terminal 5, depending on an implemented protocol(such as the well known protocol used by the Discover Zip™ cashlesspayment system).

The mobile device 3 also includes a payment account wallet applicationmodule 8 as mentioned above, which stores processing instructions usedto control the operation of the mobile device 3 to perform variousmobile payment account processes. The payment account wallet applicationmodule 8 can include an account creation sub-module and an accountactivation sub-module. The account creation sub-module and the accountactivation sub-module store processing instructions to create a requestfor a new mobile payment account if desired and to carry out a securedaccount validation and activation processes in response to user inputfrom the keypad 23 as described in the above-referenced co-pending U.S.patent application Ser. No. 12/891,866. The payment account walletapplication module 8 can also include a transaction authorizationsub-module which stores processing instructions used to control theoperation of the mobile device 3 to carry out and authorize atransaction in response to user input from the user interface 22, forexample as described in the above-referenced co-pending U.S. patentapplication Ser. No. 12/905,419. The mobile payment account walletapplication module 8 can be configured to store a plurality of walletscreens 24 which may be output on the display 25 of the user interface22 to facilitate user interaction with the sub-modules of the mobilepayment account wallet application module 8. One wallet screen can be amain menu displaying a list of user selectable options for example toaccess and manage payment account data 6 of a selected mobile paymentaccount stored on the mobile device 3. In this embodiment, a pluralityof “new product application process” wallet screens 26 are provided inthe wallet application module 8 which can be displayed in response touser selection of an option to view and apply for new mobile paymentaccount products, as will be described in more detail below. The mobiledevice 3 can also store one or more non-payment application modules 29including processing instructions used to control the operation of themobile device 3 to perform other non-payment related processes.

Also schematically illustrated in the exemplary embodiment of FIG. 2 aresecurity domains which can be implemented in the secure memory 4 of themobile device 3. The secure memory 4 is advantageously implemented to becompliant with one or more specifications of a standard infrastructurein order to facilitate communication of data and messages between themobile device 3 (and the secure memory 4) and other entities in themobile payment system 1. For example, in this embodiment, the securememory 4 is compliant with the GlobalPlatform Card Specifications(available at), and accordingly includes a plurality of security domainsfor facilitating control of the management of and accessibility tofunctionality and sensitive data associated with specific areas of thesecure memory 4 by the various entities in the mobile payment system 1.The GlobalPlatform Card Specifications (for example the “GlobalPlatformCard Specification 2.2”, March 2006, available at GPCardSpec_v2.2.pdf)define a hierarchical arrangement of security domains, each definingfunctionality and data that can be accessed by a respective associatedentity, for example cryptographic keys or certificates that can be usedto support secure channel protocol operations between the mobile device3 and the entity or entities associated with that particular securitydomain, and/or to authorize secure memory 4 content managementfunctions.

Accordingly, As shown in the exemplary embodiment of FIG. 2, a mainissuer security domain 31, associated with the account management system7 and/or the mobile payment account issuer 10, may include a paymentsecurity domain 32 associated with the payment account issuer 10, aControlling Authority (CA) security domain 34 associated with acontrolling authority in the mobile payment system 1, and aSupplementary Security Domain (SSD) code 35 associated with anintermediate security domain (not shown) to manage card content andperform cryptographic services for confidentiality. The payment securitydomain 32 in this exemplary embodiment includes wallet applicationsecure data 6 a, which includes the payment account data 6 and otherdata for use by the mobile payment account wallet application module 8.The payment security domain 32 can also include an issuer securitysub-domain 36 and one or more optional other service provider securitydomains 37. The issuer security domain 36 can include an issuer appletpackage 38, an authentication applet instance 46, and one or morepayment applet instances 40 which enable the transaction processingfunctionality using an activated mobile payment account. The paymentsecurity domain 32 may also include a Proximity Payment SystemEnvironment (PPSE) package 41 and a PPSE controller instance 42 forfacilitating an additional application layer level of control of thetransaction processing functionality between the one or more paymentapplet instances 40 and the contactless communications link interface39, and a payment package 43. In particular, the PPSE package 41 andcontroller instance 42 may be advantageously provided where the mobiledevice 3 stores a plurality of mobile payment accounts, and operate tocommunicate with the NFC reader of the merchant POS terminal 5 tocontrol which one of the payment applet instances 40, associated with arespective mobile payment account stored on the mobile device 3, is torespond back to the POS reader.

It is appreciated that each security domain will be associated with oneor more respective entities in the mobile payment system 1 depending onthe particular business model that is implemented by the system. Thespecific implementation details of the various security domains forcompliance with, for example, the GlobalPlatform Card Specifications areoutside the scope of this application and will be apparent to theskilled reader. The mobile device 3 can also include one or more otherthird party application modules 44 stored in the secure memory 4, forexample an application module related to a third party loyalty scheme.The secure memory 4 can also store a UICC applet 45 which is anapplication to manage and hold the mobile network operator'sfunctionality and secure information, such as a network key and GSM(Global Systems for Mobile Communications) PIN (Personal IdentificationNumber).

A brief description has been given above of the components forming partof the mobile payment system 1 of this embodiment. A more detaileddescription of the operation of these components in this embodiment willnow be given with reference to the flow diagram of FIG. 3, whichcomprises FIGS. 3 a to 3 d. FIGS. 3 a to 3 d provide an examplecomputer-implemented process for applying for and provisioning a mobilepayment account using the mobile device 3 in communication with theaccount management system 7. Reference is also made to FIG. 4, whichcomprises FIGS. 4 a to 4 g, schematically illustrating exemplary displayscreens that can be presented to a user on the mobile device 3 in theapplication process.

As shown in FIG. 3 a, the process begins at step S3-1 where the mobiledevice 3 receives user input to launch the mobile payment account walletapplication module 8. FIG. 4 a shows an example user interface 51 of theuser's mobile device 3 for enabling the user to launch the mobilepayment account wallet application module 8 by selection of a respectiveapplication icon 53 displayed by the handset operating system 28. Manyother forms of user interface are possible depending on the particularmobile device used to implement the present embodiment. After the userhas launched the wallet application module 8, the mobile device 3receives, at step S3-3, user selection of a menu option to search foreligible mobile payment account payment products and/or to apply for anew mobile payment account product. In the example shown in FIG. 4 b, a“main menu” wallet screen 55 is displayed by the mobile device 3 to theuser, providing a plurality of user selectable options for theelectronic wallet. The user scrolls through the list of displayedoptions to highlight 56 and select a desired menu option. In response toselection of the option to apply for a new product, the mobile device 3displays a user details input wallet screen 57 as shown in FIG. 4 c toprompt for user input of personal details, such as the user's name andaddress, into respective input fields 58. Alternatively or additionally,predetermined personal details are stored in the payment account data 6in the secure memory 4 and are automatically input to the respectivefields. Other user related information and/or search criteria can beobtained at this step for use in determining a list of eligible productsfor the user. Accordingly, at step S3-5 the mobile device 3 receivesinput of personal details and/or product search criteria and displays,at step S3-7, a list of eligible products based on the input detailsand/or search criteria. The list of eligible products is determined bythe mobile device 3, based on stored data identifying all availablemobile payment products and associated prerequisites and eligibilitycriteria. Alternatively, the determination is carried out by the accountmanagement system 7 based on the input details and/or search criteriareceived from the mobile device 3. FIG. 4 d shows an exemplary walletscreen 59 displaying a list of user selectable eligible products.

At step S3-9, the mobile device 3 receives user input of a selected 61one of the eligible mobile payment account products and in response,transmits data identifying the selected product to the accountmanagement system 7 to initiate an application process for that productto be automatically provisioned to the requesting mobile device 3 oncethe associated user has been approved by the account management system 7and/or payment account issuer 10. At step S3-11 the middleware server 16in the account management system 7 receives the request for applicationof a new mobile payment account product and in response, transmitsapplication form data for the new product back to the mobile device 3,together with a digital document including pre-application terms andconditions (T&C). It is appreciated that the pre-application terms andconditions may be particular to the product and may set out specificproduct terms that the user must review and accept before the automatedapplication process for the product can proceed. The digital documentcan be generated by the middleware server 16 in real-time, and can be acustomer specific product disclosure based on user details. In anembodiment, the digital document is generated from a template document,and populated with user-specific details. Accordingly, at step S3-13 themobile device 3 receives the application form data and the T&C digitaldocument, and may store the T&C digital document in the secure memory 4.The digital document is stored by the mobile device 3 for apredetermined amount of time, such as for 15 business days. At stepS3-15, the mobile device 3 displays the T&C digital document to theuser. FIG. 4 e shows an exemplary wallet display screen 63 displayingthe user navigatable T&C digital document, and a user input button 65that the user can press to indicate acceptance of the pre-applicationterms and conditions.

In this embodiment, the mobile device 3 is configured to transmit anindication to the middleware server 16 that the user is viewing the T&Cdigital document, at step S3-17. It is appreciated that this indicationis in the form of a data message. Alternatively, the mobile device 3 maybe configured to provide a plurality of messages to the middlewareserver 16 as the user navigates through the digital document to indicatethe user's progress through the terms and conditions. The middlewareserver 16 can be configured to automatically update the tracked progressof the user's application process in response to receipt of theindication that the T&C digital document is being viewed.

At step S3-19, the mobile device 3 receives user input indicatingacceptance of the pre-application terms and conditions. In response, themobile device 3 transmits a further indication to the middleware server16 that the user has accepted the terms and conditions, at step S3-21.The middleware server 16 is then configured to automatically update thetracked progress of the user's application process in response toreceipt of the indication that the user has accepted the pre-applicationterms and conditions. After the user has input acceptance of the termsand conditions by pressing the user input button 65, the mobile device 3displays one or more of the “apply for new product” wallet screens 26 toprompt for and receive user input of details to complete the applicationfor the desired mobile payment account product, at step S3-23. After theuser has completed the application form displayed via the “apply for newproduct” wallet screens 26, the mobile device 3 transmits the completedapplication form data to the middleware server 16 to initiate the newmobile payment account provisioning process. This provisioning processincludes approving the user's application, as well as creating,transmitting and securely storing inactive mobile payment account dataon the mobile device 3, as discussed in more detail in theabove-referenced co-pending U.S. patent application Ser. No. 12/891,866.Accordingly, at step S3-25, the middleware server 16 is arranged tocreate a new mobile payment account for the user in accordance with theuser selected mobile payment account product. In addition, the inactivemobile payment account data 6 is provisioned by the middleware server 16to the mobile device 3 and stored in the secure memory 4. If the user'sapplication for a new product cannot be automatically approved by theaccount management system 7 and/or the payment account issuer 10, theuser is notified that the decision is pending manual intervention. Oncea final decision has been made, notification that the application hasbeen approved or declined is communicated to the user, for example, viaa message transmitted to the mobile device 3 or online through a checkapplication status web page.

In this embodiment, after the inactive mobile payment account has beenprovisioned to the mobile device 3 at step S3-25, the middleware server16 transmits a post-application cardmember agreement (CMA) digitaldocument to the mobile device 3 at step S3-27, including furtherspecific product terms particular to the product that the user mustreview and accept in order to complete the application process. It isappreciated that the CMA digital document may alternatively betransmitted to the mobile device 3 together with the provisioned mobilepayment account data 6. At step S3-29, the mobile device 3 receives theCMA digital document and may store the digital document in the securememory 4. At step S3-31, the mobile device 3 displays a notification tothe user that the application for the selected product has beenapproved, together with or followed by display of the received CMAdigital document. In a similar manner as described above with referenceto the T&C digital document, the mobile device 3 is configured totransmit one or more messages to the middleware server 16 as the user isnavigating through the CMA digital document via the mobile device 3.FIG. 4 f shows an exemplary wallet screen 67 displaying the usernavigatable CMA digital document, and a user input button 69 that theuser can press to indicate acceptance of the post-application clauses ofthe agreement.

At step S3-35, the mobile device 3 receives user input indicatingacceptance of the CMA, and in response, transmits a message to themiddleware server 16 to indicate that the user has accepted thepost-application agreement. At step S3-37, the middleware server 16receives the indication of user acceptance of the CMA and can beconfigured to automatically update the tracked progress of the user'sapplication process with the indication that the user has accepted thepost-application CMA. After the user has input acceptance of the CMA,the mobile device 3 proceeds at step S3-39 to the mobile payment accountactivation process as described in the above-referenced co-pending U.S.patent application Ser. No. 12/891,866. Once the activation process hasbeen completed, the activated mobile payment account in the electronicwallet of the mobile device 3 can then be used to carry out contactlesspayment transactions as described in the above referenced co-pendingU.S. patent applications Ser. Nos. 12/891,866 and 12/905,419.

A second embodiment will now be described for facilitating furthermonitoring and tracking of the mobile payment account productapplication process. In particular, the second embodiment enablestracking of user navigation through a digital document prior to userinput of acceptance. In the embodiment described above, the mobiledevice 3 receives a digital document from the middleware server 16, forexample the T&C or CMA digital document, and waits for user input ofacceptance of terms and conditions or of the CMA. It is mentioned abovethat the mobile device 3 is configured to transmit one or more messagesback to the middleware server 16 indicating the user's progress throughthe digital document. In this embodiment, an enhanced digital documentis described with reference to FIG. 5 for facilitating enhancedmonitoring and tracking of user navigation through the document. Asshown in FIG. 5, a digital document 81 has a hierarchical documentstructure including a plurality of sections each with a respectiveheading, with a portion 82-1 of the digital document 81 being viewableat any one time via the display 25 of the mobile device 3. It isappreciated that the amount of the digital document 81 that is viewableat one time depends on the hardware capability of the mobile device 3such as the display resolution. It will be further appreciated that thedigital document 81 can be displayed as a plurality of successive pagesof the document, or alternatively can be displayed as a singlescrollable document. For example, in the digital document 81 illustratedin FIG. 5, navigation through the digital document 81 may includedisplay of an initial portion 82-1 of the document, typically the startof the document, followed by one or more intermediary portions 82-2, andfinally to a portion 82-3 corresponding to the end of the digitaldocument 81 including the user selectable button 65 to confirmacceptance of the clauses in the digital document 81. User navigationthroughout the digital document 81 does not need to be performed in alinear manner. As a further alternative, the wallet application module 8is configured to enable user configuration of the amount of the documentto be displayed, for example, via a zoom function.

In the exemplary T&C digital document illustrated in FIG. 5, threesub-sections 83-1, 83-2, 83-3 are shown corresponding to respectiveclauses indicated by the sub-headings 85-1, 85-2, 85-3. The sub-headings85 are presented at the beginning of the digital document 81 as a listof user selectable links or bookmarks to the respective position in thedigital document. The links effectively provide efficient usernavigation to the respective portion of the digital document, asillustrated by the navigation arrow 87. In this embodiment, the digitaldocument 81 includes embedded data for respective locations in thedigital document 81, illustrated schematically in FIG. 5 as dashed boxes89-1, 89-2 and 89-3 located after each section 83-1, 83-2 and 83-3,respectively in the digital document 81. When a particular portion ofthe digital document 81 associated with such an embedded data item 89 isdisplayed by the mobile device 3, the embedded data 89 triggers themobile payment account wallet application module 8 to transmit a messageto the middleware server 16 to indicate that the user has viewed thatportion of the digital document 81. In this way, the present embodimentadvantageously facilitates enhanced monitoring of user navigationthroughout a digital document and more detailed tracking of theautomated application progress.

Additionally, by providing enhanced monitoring of user navigationthroughout a digital document, the account management system 7 and thepayment account issuer 10 are able to automatically ascertain withincreased confidence that a user has thoroughly viewed thepre-application T&C and the post-application CMA terms and clauses. In afurther embodiment, the middleware server 16 can be further configuredto determine when one or more portions of a digital document has notbeen viewed by the user, and to then transmit a message to prompt forconfirmation of consent to the respective terms or clauses.

In yet a further embodiment, the mobile device 3 is further configuredto track user review of the digital documents including one or more ofmonitoring of time stamps associated with when the digital document, oreach portion of the digital document, is viewed, the areas reviewed andconsented, and the location of review for example via Global PositioningSystem functionality of the mobile device 3.

It will be understood that embodiments of the present invention aredescribed herein by way of example only, and that various changes andmodifications may be made without departing from the scope of theinvention.

In the embodiments described above, the mobile payment account isprovisioned on a mobile handset which communicates with the accountmanagement system via a cellular telephone network. Instead of a mobilehandset, other portable electronic devices configured for contactlesspayment with a merchant electronic POS, and having suitable input anddisplay means, carry out the functionality of real time applying for anew mobile payment account product, as described in the aboveembodiments. Additionally, the portable electronic device is configuredto communicate with the account activation system via any other form ofcommunication channel instead of or in addition to the above discussedover the air channels, such as a wired or wireless network connection, aBluetooth connection, or the like. Alternatively, the mobile paymentaccount data is provisioned on the portable electronic device by datatransfer via any suitable data communication path or by way of acomputer readable medium.

In the embodiments described above, the application process is carriedout automatically via a mobile device. The process of conducting andtracking the application process, and in particular of digital documentdelivery and monitoring of user navigation through a digital document,is applicable to alternative embodiments and scenarios involving one ormore additional devices other than the user's mobile device. In a firstexemplary alternative scenario, the process involves integration withthe electronic POS terminal, and the digital document may instead oradditionally be delivered to the POS to be printed out for presentationto the user. In a second alternative scenario similar to the firstscenario, the POS is integrated in the process but comprises a mobiledevice such as a portable computer or electronic tablet device. It isappreciated that in this scenario, the digital documents are formattedfor optimized display and user interaction on the target mobile device.The digital documents are then delivered to the merchant mobile devicein this scenario, in a similar manner as described above. In a thirdalternative scenario, the process is carried out from a merchant storevia an Internet or web-based kiosk. It is appreciated that in thisscenario, the digital documents are instead formatted for optimizeddisplay and user interaction via a web browser executed by the kiosk. Ina fourth alternative scenario, the process involves the user's personalcomputer interacting with the account management system via the Internetand, similar to the third scenario, the digital documents are formattedfor optimized display and user interaction via a web browser of thepersonal computer.

In the embodiments described above, the application process involvesdelivery of a pre-application T&C digital document and apost-application CMA digital document. Alternatively, a single documentis generated and transmitted to the mobile device. The digital documentis transmitted to the mobile device at any time prior to the activationprocess, or is pre-loaded onto the mobile device prior to supply to theuser, whereby the inactive provisioned mobile payment account can onlybe activated once the user has viewed and accepted the terms, conditionsand/or agreement clauses.

In the embodiments described above, the mobile device stores a pluralityof application modules (also referred to as computer programs orsoftware) in memory, which when executed enable the mobile device toimplement embodiments of the present invention as discussed herein. Thesoftware is stored in a computer program product and loaded into themobile device using any known instrument, such as removable storage diskor drive, hard disk drive, or communication interface, to provide someexamples.

In the embodiments described above, the account management system isdescribed as a separate entity to the payment account issuer and theassociated payment processing system. It is appreciated that the accountmanagement system can be provided as an integral part or sub-system ofthe payment account issuer and/or payment processing system.

Alternative embodiments may be envisaged, which nevertheless fall withinthe spirit and scope of the following claims.

1. A computer-implemented method of tracking a process of provisioning,by a middleware server to a portable device in a mobile payment system,payment account data for authorizing a payment transaction, the methodcomprising: receiving from the portable device, a user request for apayment account product; responsive to the user request, initiating aprovisioning process for the payment account product requested by theuser request, including storing status data indicative of an initiatedstate of the provisioning process; transmitting, to the portable device,a first digital document including pre-application terms and conditionsthat must be viewed and accepted by a user before the middleware serverprovisions the payment account data for the requested payment accountproduct, and updating the status data indicative of a transmitted stateof the digital document; receiving, from the portable device, anindication that the first digital document has been viewed and acceptedby the user, and in response, updating the status data indicative of aviewed and accepted state of the digital document and provisioning, tothe portable device, payment account data for an inactive paymentaccount product as requested; transmitting, to the portable device, asecond digital document including post-application agreement informationspecific to the payment account product that must be viewed and acceptedby the user, and updating the status data indicative of a transmittedstate of the second digital document; and receiving, from the portabledevice, an indication that the second digital document has been viewedand accepted by the user, and in response, updating the status dataindicative of a viewed and accepted state of the second digital documentand activating the inactive payment account product.
 2. The method ofclaim 1, wherein the portable device is arranged to display a pluralityof user-selectable payment account products that the user is eligible torequest.
 3. The method of claim 2, wherein the plurality of paymentaccount products is determined based on user details or search criteria.4. The method of claim 1, further comprising receiving an indicationthat the pre-application terms and conditions of the first digitaldocument have been acknowledged by the user before the middleware serverprovisions the payment account data for the requested payment accountproduct.
 5. The method of claim 1, wherein the digital documentcomprises data associated with one or more portions of the digitaldocument for triggering transmission of an indication that a particularportion of the digital document has been viewed and accepted.
 6. Themethod of claim 1, further comprising tracking a time of viewing one ormore portions of the digital document.
 7. The method of claim 1, furthercomprising tracking a location of viewing one or more portions of thedigital document.
 8. The method of claim 1, wherein the digital documentis formatted for the portable device.
 9. The method of claim 1, whereinthe portable device is a mobile handset.
 10. The method of claim 1,wherein the portable device is for contactless payment transactions. 11.A mobile payment account system comprising a portable device incommunication with a middleware server, wherein the middleware server isoperable to: receive a user request for a payment account product fromthe portable device; initiates, responsive to the user request asreceived, a provisioning process for the payment account productrequested by the user request, the provisioning process includingstoring status data indicative of an initiated state of the provisioningprocess; transmit, to the portable device, a first digital documentincluding pre-application terms and conditions that must be viewed andaccepted by a user before the middleware server provisions the paymentaccount data for the requested payment account product, and updates thestatus data indicative of a digital document transmitted state; receive,from the portable device, an indication that the first digital documenthas been viewed and accepted by the user and in response, update thestatus data indicative of a digital document viewed and accepted stateand provision, to the portable device, payment account data for aninactive payment account product as requested; transmit, to the portabledevice, a second digital document including post-application agreementinformation specific to the payment account product that must be viewedand accepted by the user, and update the status data indicative of thetransmitted state of the second digital document; and receive, from theportable device, an indication that the second digital document has beenviewed and accepted by the user, and in response, update the status dataindicative of a viewed and accepted state of the second digital documentand activate the inactive payment account product.
 12. A non-transitorycomputer-readable medium comprising computer-executable instructions,that when executed perform a method of tracking a process ofprovisioning, by a middleware server to a portable device in a mobilepayment system, payment account data for authorizing a paymenttransaction, when executed by respective components of a payment system,comprising: computer-implementable instructions for receiving, from theportable device, a user request for a payment account product;computer-implementable instructions for initiating, responsive to theuser request, a provisioning process for the payment account product,including storing status data indicative of an initiated state of theprovisioning process; computer-implementable instructions fortransmitting, to the portable device, a first digital document includingpre-application terms and conditions to be viewed and accepted by a userbefore the middleware server provisions the payment account data for therequested payment account product, and updating the status dataindicative of a transmitted state of the digital document;computer-implementable instructions for receiving, from the portabledevice, an indication that the first digital document has been viewedand accepted by the user, and in response updating the status dataindicative of a viewed and accepted state of the digital document andprovisioning, to the portable device, payment account data for aninactive account product as requested; computer-implementableinstructions for transmitting, to the portable device, a second digitaldocument including post-application agreement information specific tothe payment account product that must be viewed and accepted by theuser, and updating the status data indicative of the transmitted stateof the second digital document; and computer-implementable instructionsfor receiving, from the portable device, an indication that the seconddigital document has been viewed and accepted by the user, and inresponse, updating the status data indicative of a viewed and acceptedstate of the second digital document and activating the inactive paymentaccount product.